Guidelines for Pull Requests

If you haven't yet read our code review guidelines, please do so, You can find them here.

Please confirm the following by adding an x for each item (turn [ ] into [x]).

• I have removed all code style changes that are not necessary (e.g. changing blanks across the whole file that don’t need to be changed, adding empty lines in parts other than your own code)
• I am not making any changes to files that don’t have any effect (e.g. imports added that don’t need to be added)
• I do not have any sysout statements in my code or commented out code that isn’t needed anymore
• I am not reformatting any files in the wrong format or without cause.
• I am not changing file encoding or line endings to something else than UTF-8, LF
• My pull request does not show an insane amount of files being changed although my ticket only requires a few files being changed
• I have added Javadoc/documentation where appropriate
• I have added test cases where appropriate
• I have explained any part of my code/implementation decisions that is not be self-explanatory

Please provide a brief description of your ticket

It should be possible to pull in bibliography entries from citesphere

Description
Instead of entering bibliography entries by hand, the user would select entries from Citesphere and those would then be imported. Since Citesphere doesn't have a search endpoint yet, the user would when adding a bibliography block, browse their groups in citesphere and select entries to import. So:

1. user adds bibliography block on a slide
2. instead of adding a reference by hand, they log in to Citesphere (oauth authorization flow)
3. they see all groups they are part of
4. they select a group and then one or multiple references from that group
5. The selected references will be imported into VSpace
   For now, this would be a one time import. We'll worry about updating references from Citesphere later.
   The code that pull data from Citesphere should be its own plugin (have Julia create the basic plugin).

VSPC-189

Anything else the reviewer needs to know?

... describe here ...